Skip to main content

Event and Ticket Access information

Important: Access Management Under Your Control

It is crucial to highlight that menta does not intervene in the access management of your events. Access control remains entirely the responsibility of your system and team.

The QR code of the tickets we generate is the same as the one originally generated on your platform. This means these QR codes will be scanned and processed normally, without any alteration or additional adjustments required in your scanning system.

However, to ensure proper tracking and updating of ticket statuses, menta requires receiving the scanning information of the tickets. This is achieved by implementing an API call to our system immediately after a ticket has been scanned and authorized on your platform.

Individual Ticket Authorization Notification

Here is an example of how to inform menta of the authorization of a ticket, using cURL.
    curl -X POST 'https://api.mentatickets.com/v1/tickets/${ticketId}/eventAdmission'
-H 'Authorization: YOUR_API_KEY'
-H 'Content-Type: application/json'
Respuesta JSON
{
"status": 200,
"data": true,
"errors": null
}

Parameters

  • ticketId: The unique ID of the ticket that you sent to us at the time of the user’s purchase completion. This ID is internal to your platform.

Group Ticket Authorization Notification

Here is an example of how to notify menta about the authorization of a ticket, using cURL.
    curl -X POST 'https://api.mentatickets.com/v1/tickets/batch/eventAdmission'
-H 'Authorization: YOUR_API_KEY'
-H 'Content-Type: application/json'
--data-raw '[
{
"ticketId": "TICKET_ID_1",
"entryDate": "2023-09-01T12:00:00Z"
},
{
"ticketId": "TICKET_ID_2",
"entryDate": "2023-09-01T12:05:00Z"
},
{
"ticketId": "TICKET_ID_3",
"entryDate": "2023-09-01T12:10:00Z"
}
]'
Respuesta JSON
{
"status": 200,
"data": true,
"errors": null
}

Parameters

  • ticketId: The unique ID of the ticket that you sent to us at the time of the user’s purchase completion. This ID is internal to your platform.
  • entryDate: (OPTIONAL) Date of access. If not provided, the current date will be used.

Once we have this information, we can notify the user that a ticket has already been used and cannot be used again.

Reminder

Remember to use the ticket ID that you use within your platform.